Cascaded event detection modules for generating combined events interrupt for processor action

ABSTRACT

An eventpoint chaining apparatus for generalized event detection and action specification in a processing environment is described. In one aspect, the eventpoint chaining apparatus includes a first processor which has a programmable eventpoint module with an input trigger (InTrig) input. The first processing element detects an occurrence of a first processor event (p-event) and produces an OutTrigger (OT) signal. The eventpoint chaining apparatus also includes a second processor which has a programmable eventpoint module with an input trigger (InTrig) input which receives the OT signal from the first processing element. The second processing element detects an occurrence of a second p-event and produces, in response to the OT signal received from the first processing element and the detection of a second p-event, an eventpoint (EP) interrupt signal. The eventpoint chaining apparatus also includes a sequence processor interrupt control unit for receiving the EP interrupt signals indicating the occurrence of both the first and second p-events and causing a p-action in response to the occurrence of both the first and second p-events.

RELATED APPLICATIONS

This application is a divisional of U.S. Ser. No. 09/598,566 filed Jun. 21, 2000, now U.S. Pat. No. 6,735,690 and claims the benefit of U.S. Provisional Application Ser. No. 60/140,245 filed Jun. 21, 1999 which are incorporated by reference herein in their entirety.

FIELD OF THE INVENTION

The present invention relates generally to improved techniques for processor event detection and action specification using a generalized mechanism.

BACKGROUND OF THE INVENTION

A processor event or p-event may be defined as some change of state that it is desirable to recognize. The acknowledgement of a processor event may be termed a processor action or p-action. The purpose of the event-action mechanism, or eventpoint, is to synchronize various actions with specific program and/or data flow events within the processor. Examples of eventpoints which may be encountered include reaching a specified instruction address, finding a specific data value during a memory transfer, noting the occurrence of a particular change in the arithmetic condition flags, accessing a particular memory location, etc. Eventpoints can also include a linked sequence of individual eventpoints, termed chaining, such as finding a specific data value after reaching a specified instruction address, or reaching a second specified instruction address after reaching a first specified instruction address. The p-actions can include changing the sequential flow of instructions, i.e., vectoring to a new address, causing an interrupt, logging or counting an event, time stamping an event, initiating background operations such as direct memory access (DMA), caching prefetch operations, or the like.

In previous approaches, each p-event and its consequent p-action typically was treated uniquely and separately from other specific event-actions in order to solve some special problem. One of the many new contributions the architecture of the present invention provides is a generalized eventpoint mechanism. A requirement of the traditional sequential model of computation is that the processor efficiently handle the programming constructs that affect the sequential flow of instructions to be executed on the processor. In the prior art, one of these programming constructs is an auto-looping mechanism, which is found on many digital signal processors (DSPs). Auto-looping is employed to change the program flow for repetitive loops without the need for branch instructions, thereby improving the performance of programs that use loops frequently. Nested loops have also been supported in the prior art.

It has also been found imperative that a processor support facilities to debug a program. In the prior art, the capability of setting breakpoints on instructions, data, or addresses that cause a branch to a specified target address or cause an interrupt has been developed. The interrupt or debug branch directs the program flow to a special program that provides debug operations to aid the programmer in developing their software.

In another example, it has also been found imperative that a processor support facilities for initiating a DMA operation to occur in the background of normal program execution. In the past, the background DMA capability was typically initiated by specific DMA instructions or instructions specialized for DMA by nature of the side effect that they cause.

Consequently, auto-looping, background DMA operation, debug breakpoint capability, and other unique p-events and their consequent p-actions, represent approaches that have been considered separately in the prior art. The present invention generalizes these functions and provides additional unique capabilities that arise due to the generalization of the various p-events and p-actions in a common architecture thereby providing a common design and program approach to the development and use of all of these types of functions.

SUMMARY OF THE PRESENT INVENTION

The present invention addresses the need to provide a processor with a generalized p-event and p-action architecture which is scalable for use in a very long instruction word (VLIW) array processor, such as the ManArray processor. In one aspect of the invention, generalized p-event detection facilities are provided by use of a compare performed to discover if an instruction address, a data memory address, an instruction, a data value, arithmetic-condition flags, and/or other processor change of state eventpoint has occurred. In another aspect of this invention, generalized p-action facilities are provided to cause a change in the program flow by loading the program counter with a new instruction address, generating an interrupt, generating a log, counting the p-event, passing a parameter, etc. The generalized facilities may be advantageously defined in the eventpoint architecture as consisting of a control register and three eventpoint parameters: 1) a register to compare against, 2) a register containing a second compare parameter, vector address, or parameter to be passed, and 3) a count or mask register. Based upon this generalized eventpoint architecture, new capabilities are supported that extend beyond typical prior art capabilities. For example, auto-looping with capabilities to branch out of a nested auto-loop upon detection of a specified condition, background DMA facilities, and the ability to link a chain of p-events together for debug purposes, among others are all new capabilities easily obtained by use of this invention.

A more complete understanding of the present invention, as well as other features and advantages of the invention, will be apparent from the following Detailed Description and the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an exemplary 2×2 ManArray iVLIW processor suitable for use in conjunction with the present invention;

FIG. 2A illustrates an exemplary load from special purpose register (LSPR) instruction encoding;

FIG. 2B illustrates an exemplary load from special purpose register syntax/operation description;

FIG. 3A illustrates an exemplary store to special purpose register (SSPR) instruction encoding;

FIG. 3B illustrates an exemplary store to special purpose register syntax/operation description;

FIG. 4 illustrates an exemplary placement of eventpoint registers in an special purpose register file (SPRF) in accordance with the present invention;

FIG. 5 illustrates an exemplary instruction eventpoint high level logic flow diagram;

FIGS. 6A–6G illustrate exemplary decode and control logic descriptions for instruction eventpoint modules in accordance with the present invention;

FIG. 7A illustrates an exemplary event point loop (EPLOOP) instruction encoding in accordance with the present invention;

FIG. 7B shows a syntax/operation table for the EPLOOP instruction of FIG. 7A;

FIG. 7C illustrates an exemplary event point loop immediate (EPLOOPI) instruction encoding in accordance with the present invention;

FIG. 7D shows a syntax/operation table for the EPLOOPI instruction of FIG. 7C;

FIG. 8 illustrates a ManArray pipeline timing diagram for the EPLOOP instruction of FIG. 7A;

FIG. 9 illustrates an exemplary data eventpoint high level logic flow diagram;

FIGS. 10A–10J illustrate exemplary decode and control logic descriptions for data eventpoint modules in accordance with the present invention;

FIG. 11 illustrates an exemplary eventpoint chaining apparatus in accordance with the present invention; and

FIGS. 12A–12C illustrate aspects of an exemplary background DMA eventpoint program in accordance with the present invention.

DETAILED DESCRIPTION

Further details of a presently preferred ManArray core, architecture, and instructions for use in conjunction with the present invention are found in

U.S. patent application Ser. No. 08/885,310 filed Jun. 30, 1997, now U.S. Pat. No. 6,023,753,

U.S. patent application Ser. No. 08/949,122 filed Oct. 10, 1997,

U.S. patent application Ser. No. 09/169,255 filed Oct. 9, 1998,

U.S. patent application Ser. No. 09/169,256 filed Oct. 9, 1998,

U.S. patent application Ser. No. 09/169,072 filed Oct. 9, 1998,

U.S. patent application Ser. No. 09/187,539 filed Nov. 6, 1998,

U.S. patent application Ser. No. 09/205,558 filed Dec. 4, 1998,

U.S. patent application Ser. No. 09/215,081 filed Dec. 18, 1998,

U.S. patent application Ser. No. 09/228,374 filed Jan. 12, 1999,

U.S. patent application Ser. No. 09/238,446 filed Jan. 28, 1999,

U.S. patent application Ser. No. 09/267,570 filed Mar. 12, 1999,

U.S. patent application Ser. No. 09/337,839 filed Jun. 22, 1999,

U.S. patent application Ser. No. 09/350,191 filed Jul. 9, 1999,

U.S. patent application Ser. No. 09/422,015 filed Oct. 21, 1999,

U.S. patent application Ser. No. 09/432,705 filed Nov. 2, 1999,

U.S. patent application Ser. No. 09/471,217 filed Dec. 23, 1999,

U.S. patent application Ser. No. 09/472,372 filed Dec. 23, 1999,

U.S. patent application Ser. No. 09/596,103, filed Jun. 16, 2000, now U.S. Pat. No. 6,397,324,

U.S. patent application Ser. No. 09/598,567, filed Jun. 21, 2000,

U.S. patent application Ser. No. 09/598,564 filed Jun. 21, 2000, now U.S. Pat. No. 6,662,234,

U.S. patent application Ser. No. 09/598,558, filed Jun. 21, 2000, and

U.S. patent application Ser. No. 09/598,084 filed Jun. 21, 2000, as well as,

Provisional Application Ser. No. 60/113,637, filed Dec. 23, 1998,

Provisional Application Ser. No. 60/113,555, filed Dec. 23, 1998,

Provisional Application Ser. No. 60/139,946, filed Jun. 18, 1999,

Provisional Application Ser. No. 60/140,245, filed Jun. 21, 1999,

Provisional Application Ser. No. 60/140,163, filed Jun. 21, 1999,

Provisional Application Ser. No. 60/140,162, filed Jun. 21, 1999,

Provisional Application Ser. No. 60/140,244, filed Jun. 21, 1999,

Provisional Application Ser. No. 60/140,325, filed Jun. 21, 1999,

Provisional Application Ser. No. 60/140,425, filed Jun. 22, 1999,

Provisional Application Ser. No. 60/165,337, filed Nov. 12, 1999,

Provisional Application Ser. No. 60/171,911, filed Dec. 23, 1999,

Provisional Application Ser. No. 60/184,668, filed Feb. 24, 2000,

Provisional Application Ser. No. 60/184,529, filed Feb. 24, 2000,

Provisional Application Ser. No. 60/184,560, filed Feb. 24, 2000,

Provisional Application Ser. No. 60/203,629, filed May 12, 2000, and

Provisional Application Ser. No. 60/121,987 filed Jun. 21, 2000, respectively, all of which are assigned to the assignee of the present invention and incorporated by reference herein in their entirety.

In order to support generalized p-event detection, p-event counting, and p-action flow control or parameter passing, a minimum of two parameters are used with generally three parameters utilized. These three general parameters are defined in the eventpoint architecture as a first register to compare against, a second optional register containing either a second compare parameter, a vector address, or parameter to be passed, and a third register acting as a p-event counter or a mask. To allow flexibility in the control of how these three parameters are used, a control register is employed for each eventpoint set of the three parameters. The control register content specifies the type of comparison that is to be made and defines the action to be taken. For example, an eventpoint can be uniquely identified when a compare match occurs between the first compare register parameter and a specified processor state, or when a chain of eventpoints occurs in some logical or sequential fashion. Some of the possible processor states that can be compared for include an instruction address, a specific instruction, a VLIW Memory (VIM) address, a data memory address, a memory or register file data value, flags, a control register value, and the like. The control register also defines how the eventpoint is to be treated and the p-action that is to occur. Some p-actions make use of the second register parameter. For example, the second register parameter can contain a vector address that is loaded in the program counter upon a p-event detection, thereby directing the program to a debug routine or the beginning of a program loop. Other examples include: starting a background operation at an eventpoint, such as a DMA operation, and using the second parameter register to pass a variable to the DMA hardware, generating an interrupt at the eventpoint and using the second parameter register to pass a variable to the interrupt routine, and the like. Other p-actions include counting the p-event, link to and enable another eventpoint, etc. The determination of whether a p-event is used directly to cause a p-action, or whether multiple occurrences of the same p-event are required before causing a p-action, is made by the control register in conjunction with the third count parameter. The eventpoint counter is tested for a zero state, a one state, or other state indicating it contains some count value. These three states can be tested for at different eventpoints and different p-actions can result. An eventpoint (EP) auto-loop with unique capabilities can be specified as a subset of the capabilities of the present invention. For example, an EP auto-loop can be set up that skips the loop completely if the count is zero at the loop start address, or an auto-loop can be set up that allows a conditional exit from the auto-loop based upon the state of an arithmetic condition flag.

It is noted that depending upon the application, the scope of and requirements for the generalized eventpoint hardware can vary. Consequently, it is desirable to have a standard architectural approach for implementation and programmer use. To demonstrate the apparatus and use of this invention in the context of a presently preferred processor, the next sections describe in detail the incorporation of this generalized eventpoint architecture into the scalable indirect-VLIW ManArray processor.

In a preferred embodiment of the present invention, a ManArray 2×2 iVLIW single instruction multiple data stream (SIMED) processor 100 shown in FIG. 1 contains a controller sequence processor (SP) combined with processing element-0 (PE0) SP/PE0 101, as described in further detail in U.S. application Ser. No. 09/169,072 entitled “Methods and Apparatus for Dynamic Merging an Array Controller with an Array Processing Element”. Three additional PEs 151, 153, and 155 are also utilized to demonstrate the generalized processor event detection and action specification architecture and design apparatus for the present invention.

The SP/PE0 101 contains a fetch controller 103 to allow the fetching of short instruction words (SIWs), also known as native instructions, from a B=32-bit instruction memory 105. The fetch controller 103 provides the typical functions needed in a programmable processor, such as a program counter (PC), branch capability, eventpoint (EP) loop control operations, support for interrupts, and also provides the instruction memory control which could include an instruction cache if needed by an application. In addition, the SIW I-Fetch controller 103 dispatches 32-bit SIWs to the other PEs in the system by means of the 32-bit instruction bus 102.

In this exemplary system, common elements are used throughout to simplify the explanation, though actual implementations need not be so limited. For example, the execution units 131 in the combined SP/PE0 101 can be separated into a set of execution units optimized for the control function, for example, fixed point execution units, and the PE0 as well as the other PEs 151, 153 and 155 can be optimized for a floating point application. For the purposes of this description, it is assumed that the execution units 131 are of the same type in the SP/PE0 and the other PEs. In a similar manner SP/PE0 and the other PEs are shown as all using a five instruction slot iVLIW architecture which contains a very long instruction word memory (VIM) 109 and an instruction decode and VIM controller function unit 107 which receives instructions as dispatched from the SP/PE0's I-Fetch unit 103 and generates the VIM addresses-and-control signals 108 required to access the iVLIWs stored in the VIM. Store, load, arithmetic logic unit (ALU), multiply accumulate unit (MAU), and data select unit (DSU) instruction types are identified by the letters SLAMD in VIM 109 as follows; store (S), load (L), ALU (A), MAU (M), and DSU (D). The loading of the iVLIWs is described in further detail in U.S. patent application Ser. No. 09/187,539 entitled “Methods and Apparatus for Efficient Synchronous MIMD Operations with iVLIW PE-to-PE Communication”. Also contained in the SP/PE0 and the other PEs is a common PE configurable register file 127 which is described in further detail in U.S. patent application Ser. No. 09/169,255 entitled “Methods and Apparatus for Dynamic Instruction Controlled Reconfiguration Register File with Extended Precision”.

Due to the combined nature of the SP/PE0, the data memory interface controller 125 must handle the data processing needs of both the SP controller, with SP data in memory 121, and PE0, with PE0 data in memory 123. The SP/PE0 controller 125 also is the source of the data that is sent over the 32-bit or 64-bit (depending upon implementation) broadcast data bus 126 and contains a special purpose register file (SPRF) and instruction and data eventpoint modules described in this invention. The other PEs, 151, 153, and 155 contain common physical data memory units 123′, 123″, and 123″ though the data stored in them is generally different as required by the local processing done on each PE. The interface to these PE data memories is also a common design in PEs 1, 2, and 3 and indicated by PE local memory and data bus interface logic 157, 157′ and 157″. The interface logic units 157, 157′, and 157″ also contain the PEs SPRF and data eventpoint modules described further below. Interconnecting the PEs for data transfer communications is the cluster switch 171 more completely described in U.S. Pat. No. 6,023,753 entitled “Manifold Array Processor”, U.S. patent application Ser. No. 08/949,122 entitled “Methods and Apparatus for Manifold Array Processing”, and U.S. patent application Ser. No. 09/169,256 entitled “Methods and Apparatus for ManArray PE-to-PE Switch Control”. The interface to a host processor, other peripheral devices, and/or external memory can be implemented in many ways. The primary mechanism shown for completeness is contained in a direct memory access (DMA) control unit 181 that provides a scalable ManArray data bus 183 that connects to devices and interface units external to the ManArray core. The DMA control unit 181 provides the data flow and bus arbitration mechanisms needed for these external devices to interface to the ManArray core memories including the VIM via the multiplexed bus interface represented by line 185. A high level view of the ManArray control bus (MCB) 191 is also shown.

All of the above noted patents and applications are assigned to the assignee of the present invention and incorporated herein by reference in their entirety.

Generalized Eventpoint Description

Each eventpoint specifies a set of one or more p-events which are to be monitored and the associated p-actions to perform when they occur. As part of the architecture definition, the eventpoints are separated into two basic classes: instruction eventpoints and data eventpoints. This separation allows a better utilization of the control register that specifies the eventpoints, though having a bit in the control register that selects instruction or data type eventpoints is not precluded. Both classes of eventpoint parameters and controls are stored in registers located in a ManArray special purpose register file (SPRF). SPRs are registers that provide specialized control and/or communication capabilities to the array processor. Most SPRs are accessible by the SP, but some are implemented in both the SP's SPR address space and in the PE's SPR address space. These registers are accessible in 1-cycle by the SP (or PE) when using the Load SPR (LSPR) instruction encoding format 200 shown in FIG. 2A, or store SPR (SSPR) instruction, having encoding format 300 of FIG. 3A. Syntax/operation tables 210 and 310 for these instructions are shown in FIGS. 2B and 3B, respectively. The LSPR instruction loads a byte, half-word, or word operand into an SP target register from an SP special-purpose register or into a PE target register from a PE special-purpose register. The SPR to load from is specified by its SPR Address SPRADDR. The SSPR instruction stores a byte, half-word, or word operand to an SP special-purpose register from an SP source register or to a PE special-purpose register from a PE source register. The SPR being stored to is specified by its SPR Address SPRADDR.

The SP and each PE contains an SPR file, each optimized according to its use. FIG. 4 shows an exemplary SPR register map 400 providing details of the placement of the instruction and data eventpoint registers in the ManArray SPR address space. The leftmost column 401 contains the specific system addresses for the eventpoint registers 410 as seen from the ManArray control bus (MCB). The next column 403 has the core SP/PE addresses for the eventpoint registers 410 as identified in the rightmost three columns 405, 407 and 409. The eventpoint SPRs have a guaranteed single cycle access. The primary mechanism to access to the SPRs is through the use of load and store SPR instructions that move data between the compute register file (CRF) and the SPRs. It is also possible to set the eventpoints via a system ManArray control bus (MCB). In that case, it takes multiple cycles to set up an eventpoint.

Even though no architecture limit is set for the total number of eventpoints that can be implemented, there is a practical limit dictated by the functionality desired. For example, one ManArray implementation specifies six instruction and three data eventpoints in the SP and a single data eventpoint in each PE. It is noted that each eventpoint has associated with it a small 8-bit control register and up to three parameter registers. The ManArray implementation is used as one suitable and presently preferred implementation in the description of the invention which follows.

Instruction Eventpoints

An instruction eventpoint (IEP) implementation is described first. FIG. 5 depicts an exemplary instruction eventpoint module 500 having three eventpoint registers, comprising two half-word 16-bit registers 516 and 518, and two other eventpoint registers 524, and 528, an 8-bit control register 514 comprising a plurality of instruction eventpoint control bits, eventpoint decode and control logic 510 and the interfaces necessary for implementing the generalized instruction eventpoint architecture of the present invention. The IEPxR2.H0 register 518 is operable as a counter whose initial count value is loadable under program control. The plurality of instruction eventpoint control registers are byte-wide registers with one such assigned for each instruction eventpoint, for example, register 514. The eventpoint control registers for up to eight instruction eventpoints are stored in two 32-bit registers, IEPCTL0 and IEPCTL1, located in the SP SPR file and formatted as shown in the tables below:

IEPCTL0 Register Reset Value = 0x00000000 3 3 2 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 S P T IEP3 S P T IEP2 S P T IEP1 S P T IEP0 3 3 3 2 2 2 1 1 1 0 0 0

IEPCTL1 Register Reset Value = 0x00000000 3 3 2 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 S P T IEP7 S P T IEP6 S P T IEP5 S P T IEP4 7 7 7 6 6 6 5 5 5 4 4 4 Reserved in Example System Each evenpoint “x” has associated with it an IEPx control byte that specifies how the three evenpoint parameter registers IEPxR0, IEPxR1 and IEPxR2 are used for detecting instruction events and generating corresponding actions as explained further below. Each control byte is made up of a three bit field labeled (SPT) and a five bit field labeled with the instruction event point number (IEPx). The SPT encoding and meanings are given in the follow table:

Code (SPT) Meaning 000 No EP Interrupt, OutTrigger

InTrigger, InTriggerFF always set 001 No EP Interrupt, OutTrigger

InTrigger, InTriggerFF from InTrigger 010 No EP Interrupt, OutTrigger

control logic, InTriggerFF always set 011 No EP Interrupt, OutTrigger

control logic, InTriggerFF from InTrigger 100 EP Interrupt, OutTrigger

InTrigger, InTriggerFF always set 101 EP Interrupt, OutTrigger

InTrigger, InTriggerFF from InTrigger 110 EP Interrupt, OutTrigger

control logic, InTriggerFF always set 111 EP Interrupt, OutTrigger

control logic, InTriggerFF from InTrigger In general, the control logic for each eventpoint receives an input trigger signal from a predecessor eventpoint and generates a trigger signal output to a successor eventpoint. In the exemplary ManArray implementation, all SP resident eventpoints (IEP0–IEP5 and SP DEP0–DEP2) are inked in a circular chain so that it is possible to support chaining of the eventpoints. The SPT bits are defined as follows:

S Signal bit. Used to control output signal generation from eventpoint logic. This bit is primarily used to indicate whether or not an EP interrupt signal will be generated when the specified event occurs, but may be used for other purposes for some specialized types of event points. P Pass-through control bit. This bit is most commonly used to indicate pass-through of the InTrigger signal from input to output. If this bit is a “0”, then the InTrigger signal is passed from input to output of the eventpoint logic. If this bit is a “1” then the InTrigger signal is not passed to the output of the eventpoint logic. T Trigger function bit. This bit is used to control the use of the InTrigger and/or InTriggerFF signals within the eventpoint logic. Its use is dependent on the control code (IEPx fields). The term InTrigger refers to an input signal representing that a p-event has been detected. The term InTriggerFF refers to a latched signal to enable event monitoring. OutTrigger refers to an output control signal indicating a p-event has been detected, and EP Interrupt refers to whether an eventpoint interrupt is specified to occur on detecting the eventpoint. The detection of a p-event is indicated in the generation of an OutTrigger signal which is connected to the InTrigger input of the next eventpoint logic module to allow chaining of eventpoints. EP Interrupt is an output of an eventpoint module that can be enabled to cause an interrupt depending upon the encoding of the eventpoint control. In the exemplary ManArray architecture, the eventpoint interrupt is also termed the debug interrupt. The following table describes these signals in greater detail:

InTriggerFF The InTrigger flip-flop is a non-programmer-visible register bit used to enable event monitoring. The control of this bit depends on the value programmed into the event point control register ‘T’ bit, and on the event point operation code (IEPx). InTrigger This signal is used to designate the unlatched input trigger signal which is the OutTrigger signal from the previous event point module in the chain (see eventpoint chaining description). OutTrigger This non-programmer visible signal is an output from an event point control logic or from the InTrigger signal. The source of this signal depends on the setting of the ‘S’ bit and the operation code in the event point's control field. EXTOUT This signal is asserted in Data Event Point control modes when the event point counter is being used as a semaphore and an address match has occurred with a non-zero count present. (In the example implementation this is used for DMA data flow control and these signals are connected to inputs in the DMA controller which cause semaphore increments). EP Interrupt This is a signal which allows the generation of an eventpoint interrupt (also known as a debug interrupt) based on the occurrence of a detected event. The source of this signal depends on the setting of the ‘S’ bit and the operation code in the event point's control field. Operation utilizing these signals is illustrated in FIG. 5 and described in more detail in the following sections. In FIG. 5, the programmer/compiler specified content of the control register 514 is one of the byte fields from the 32-bit IEPCTL0 or IEPCTL1. The eventpoint control information is conveyed on the 8-bit output of the {SPT, IEPx} byte register on signal lines 529 to the decode and control logic 510.

Details for the three other eventpoint registers 524, 528, and the half-word 16-bit registers 516 and half-word counter register 518 for eventpoint “x” are shown in more detail in the tables below:

IEPxR0 3 3 2 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 IEPxR0.W (compare value)

IEPxR1 3 3 2 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 IEPxR1.W (compare value)

IEPxR2 3 3 2 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 IEPxR2.H1 IEPxR2.H0 Reload Count Event Count IEPxR0 524 holds a programmer-specified value, that had been loaded via a store to special purpose register (SSPR) instruction, as illustrated in FIGS. 3A and 3B, over the SPR bus 517, which consists of address, data, and control, that is to be compared with a selected bus signal 521. Multiplexer 534 selects either the instruction fetch address bus 519 or other implementation specific bus signal 557 by means of multiplexer control signal 563. The multiplexer control signal 563 is generated based upon the decoding of the eventpoint control register IEPCTLz.By 514 contents, where z=0 or 1 and By represents the yth control byte of the 32 bit IEPCTLz control register. IEPxR0 524 contains either an address value (an instruction fetch address, a load unit's effective address, or a store unit's effective address) or an instruction as a data value. The exemplary implementation, though not architecturally limited to this, shown in FIG. 5 provides for two compare IEPxR0 paths: the instruction fetch address bus 519 and the other bus signal 557 which could be an instruction bus, for example.

For use in EP auto-loop constructs, the IEPxR0 register 524 is loaded, via the SSPR instruction, with the address of the last instruction in a program loop. During each instruction fetch, the contents of the IEPxR0 register 524 are compared with the instruction fetch address. When comparator 526 detects a match as indicated by signal 539, then, if the count value in the associated IEPxR2.H0 counter register 518 is greater than one, the program counter is loaded with the contents of the associated IEPxR1 register 528, which contains the address of the first instruction in the EP loop, to start a new iteration of the EP loop. The value stored in the IEPxR1 register 528 represents the programmer-specified value that had been loaded via the SSPR instruction either over the SPR bus 517, which consists of address, data, and controls, or the instruction fetch address bus 519 as selected by multiplexer 530 under control of the decode and control logic 510 and control output signal 561. The value loaded into the IEPxR1 register 528 is either passed to a background operation, over the EPxBus 551 or is used as an address to be loaded into the program counter (PC) as is done in eventpoint looping, using the EPxBus 551, to change the flow of the program to a new start address. The value placed upon the EPxBus 551 is accompanied by a load EPxBus signal 549. The IEPxR2 register is split into two half-word portions IEPxR2.H1 516 and IEPxR2.H0 518. The IEPxR2.H0 counter register 518 portion contains a programmer specified count value that is counted down on the detection of each event by counter hardware included in register 518. Certain eventpoints can cause the counter to be incremented. The counter register is useful for the counting of events and indicating if a count is pending or if, on a count down operation, it has reached a 1 or a 0. The count pending output, count=1 or count=0 situation is detected in detector block 522 connected to counter register output 235 and the appropriate signal 537 is sent to the decode and control logic 510. Both halfword portions of IEPxR2 are loaded over the SPR bus 517, which consists of address, data, and controls, and the IEPxR2.H0 portion can also be loaded with the IEPxR2.H1 value 531 as selected by multiplexer 520 to pass through to input 533, depending upon the event as controlled by the decode and control logic 510 based upon the control register 514. For example, in EP auto-loops when the end of the EP loop is reached, or, in other words, the IEPxR2.H0 is equal to 1 and the address in the associated IEPxR0 register matches the instruction fetch address, the contents of IEPxR2.H0 are replaced with the reload count IEPxR2.H1. Another option available to the eventpoint logic is to cause an EP interrupt 547 that changes the program flow to an EP interrupt routine useful for analysis and problem solving.

The operation of decode and control logic 510 is discussed below in connection with exemplary decode and control logic descriptions 600, 640, 650, 660, 670, 680, and 690 shown in FIGS. 6A–6G, where the control value, {Sx, Px, Tx, IEPx}, represents the byte control field loaded in control register 514 and is shown as SPTxxxxx. An operation column 601 of the tables describes the operation of the decode and control logic 510, use of the inputs, and specifies the output generation. A control value column 602 contains a functional description of the operation.

FIG. 6A will be explained in detail to describe the general operation of the eventpoint logic. On power on, line 603, the control value for eventpoint ‘x’ is ‘00000000’ which indicates the eventpoint ‘x’ is disabled, no action is to be specified, and the InTrigger signal 515 of FIG. 5 is passed through the multiplexer 508 to the OutTrigger signal 545. When the IEPCTLz.By control byte is loaded with a value ‘00T11000’ 604, the eventpoint is enabled to eventpoint looping, skip the loop if the count is zero, and if T=1 then InTrigger can be used to exit or skip the loop. In the operation description 601, pseudo code describes the control logic for this control code encoding. The symbols used are as follows: // precedes comments, == is the equality operator, && is the logical AND operator, ∥ is the logical OR operator, and A←B indicates the signal A or register A is assigned the value of the signal B or register B, respectively. Beginning at the top of FIG. 6A and noting references to FIG. 5, line 605 indicates the OutTrigger signal 545 is always assigned the InTrigger signal 515. The next two lines 606 and 607 indicate that if T=1, then the InTriggerFF 512 is set by the InTrigger signal 515. If this occurs, then the logic can exit or skip the loop dependent upon a previous event OutTrigger. This external event trigger is termed eventpoint chaining and is described in further detail below. Lines 608 and 609 cover the case where T=0. When T=0, then the InTriggerFF is set to a “1” which enables this eventpoint module and does not react to any external trigger event. Line 610 indicates that “When” the value in the program counter (PC), or, in other words, the instruction fetch address, equals the value stored IEPxR0 OR the value of the PC equals the value stored in IEPxR1, then some type of action is to be taken. It is noted that for use in eventpoint looping the value stored in IEPxR0 is the last instruction in a program loop and the value stored in IEPxR1 is the first instruction of the program loop. Statement 610 indicates that when the program counter reaches either the start of a program loop or the last instruction in a program loop some p-action is to be taken. When this compare point is reached, the next line 611 indicates a compare 532 of the instruction fetch address 519 with the IEPxR1 551 which at the match point indicates the program counter has reached the first instruction of a loop. If this compare is true AND either the trigger is enabled AND active (line 612) OR the loop count is zero (line 613), then the p-action of lines 614–617 is to occur. Line 614 indicates the PC is loaded with the end of loop address, causing a jump to the end of the loop. The loop counter is reinitialized as indicated in line 615 and the InTriggerFF is cleared in line 616 to prepare it for another event detection. It is noted that since the PC was directed to the last instruction in the loop and the loop is to be bypassed this “last instruction in the loop” is canceled in line 617. It is further noted that this canceling procedure was done in this exemplary implementation to avoid a timing path problem with having an adder in the path to load “last instruction in the loop+1”. Alternative implementations may choose to implement this adder scheme which is also supported by the present invention. When the program counter indicates a match with the loop end address, line 618, through a compare of the instruction fetch address 519 and IEPxR0 525, then the program sequence can either 1) fall out of the loop if a different trigger event has occurred, 2) fall out of the loop if the loop count indicates the loop has been completed or is zero for the single instruction loop case, or 3) branch back to the beginning of the loop if the loop is not complete. The next logic segment, lines 619–622, represents the logic and actions that are to occur if a different trigger event has occurred. In line 619, the requirement is: if T=1 AND InTriggerFF==1 which if true indicates the trigger is enabled and active. In FIG. 5, this logic is in the decode and control logic block 510 which receives input 527 from the InTriggerFF (InTFF) register 512. Given line 619 is true, then falling out of the loop, with a good probability that the number of loop iterations did not complete, is accomplished by line 620 which requires the hardware to load the program counter with the next sequential program step, i.e., taking the program away from the loop. In addition, line 621 requires the eventpoint to be reinitialized in case the loop is entered again by loading the loop reload count stored in IEPxR2.H1 into IEPxR2.H0. This reload path is implemented in FIG. 5 by lines 531 which connect the output of the reload count register IEPxR2.H1 to a multiplexer 520 which multiplexes this output with a signal on programming SPR path 517, which consists of address, data, and controls, as selected by the decode and control logic 510 to place the reload count value on the multiplexer output 533 for loading into the loop counter register 518 IEPxR2.H0. Further, the trigger event which caused the loop to exit is reset as indicated in line 622. The second case is covered by the “else” clause of line 623 which indicates a hardware compare of the loop counter output testing for a zero or one count. In FIG. 5, this is implemented in hardware in block 522 that tests the output of the IEPxR2.H0 counter register 518 and sends the results to the decode and control block 510. If this situation is detected, then the loop is to be exited due to count completion, or if the loop count had been loaded with a zero, then the program loop is not to be repeated. Consequently, line 624 requires the program counter to be loaded with the next sequential program address and line 625 requires the loop count to be reinitialized to the value stored in the reload count IEPxR2.H1. If these conditions are not met, line 626, then the loop count is neither a 0 nor a 1 and since the program counter is at the last instruction in the loop the loop is to be repeated. Consequently, the program counter is loaded with the loop “start” address IEPxR1 627. This loading is accomplished by sending the start address IEPxR1 value on the EPxBus 551 and a load EPxBus signal 549 to the program counter causing the PC to be loaded and directing the program flow back to the beginning of the loop. Line 628 indicates the loop counter register 518 is to be decremented indicating the loop has completed another execution sequence. This ends the logic operation description of what happens when the PC is at the end address of a loop.

FIGS. 6B–6G illustrate other forms of instruction eventpoint operations providing a programmer with unique capabilities due to the general approach taken for the architecture. For example, FIGS. 6C and 6D illustrate the logic operation for loop operations that can exit based on the state of the F0 arithmetic condition flag. FIG. 6E represents the logic operation for generating an EP or debug interrupt with optional pre-count and pre-trigger. The approach of FIG. 6F is useful for vectoring or branching to a target address after count matches have occurred. The approach of FIG. 6G is used to generate an EP interrupt after count InTriggers have been received. It will be appreciated that other eventpoint operations are easily achieved for numerous purposes using this architectural and programming approach for eventpoints.

Another aspect of this invention regards handling single instruction loops where the loop start address and loop end address are the same. To ensure correct operation, the instruction eventpoints have a priority associated with them to handle situations where more than one eventpoint asserts its control to load the PC with the next fetch address. The priority is chosen such that when a program uses nested loops that share starting and/or ending addresses, the inner most loop should be the lowest numbered eventpoint. The priority is as follows:

-   1) eventpoint 0 load of PC with IEP0R1 * -   2) eventpoint 1 load of PC with IEP1R1 * -   3) eventpoint 2 load of PC with IEP2R1 * -   4) eventpoint 3 load of PC with IEP3R1 * -   5) eventpoint 4 load of PC with IEP4R1 * -   6) eventpoint 5 load of PC with IEP5R1 * -   7) eventpoint 5 load of PC with IEP5R0 -   8) eventpoint 4 load of PC with IEP4R0 -   9) eventpoint 3 load of PC with IEP3R0 -   10) eventpoint 2 load of PC with IEP2R0 -   11) eventpoint 1 load of PC with IEP1R0 -   12) eventpoint 0 load of PC with IEP0R0     For the asterixed items above, this priority is used in the logic     provided that one of the two following statements is true:     -   a) the eventpoint is configured as a loop and no higher numbered         eventpoint asserts control to skip a loop, or     -   b) for those alternative uses of the eventpoint logic, the         eventpoint is not configured as a loop.         Eventpoint Looping

To minimize the number of set-up cycles, specialized instructions, a set up and execute an instruction eventpoint loop (EPLOOPx) instruction encoding 700 shown in FIG. 7A and a set up and execute an instruction eventpoint loop immediate (EPLOOPIx) instruction encoding 720 shown in FIG. 7C may be advantageously employed. The syntax/operation descriptions 710 and 730 for these instructions are shown in FIGS. 7B and 7D, respectively. The EPLOOPx instruction 700 sets up and executes a program loop beginning with the next sequential instruction. The instruction eventpoint register (IEPxR1) is loaded with the address of the next sequential instruction, representing the start address of the first instruction in the loop. The instruction event point register (IEPxR0) is loaded with the address of the last instruction in the loop, which is the sum of the address of the LOOP instruction and a 10-bit unsigned displacement UDISP10 which is produced in the assembly using a label. The appropriate instruction eventpoint control field IEPx, IEP0–IEP3, in the IEPCTL0 register is loaded with the hexadecimal value 0x18. If the loop counter (IEPxR2.h0) is non-zero, execution proceeds with the next sequential instruction. If the loop counter is zero, the body of the loop is skipped and execution proceeds with the next sequential instruction after the address in IEPxR0. While a loop is active (Loop Counter>0) each instruction address is compared to the IEPxR0. When there is a match and Loop Counter>1, PC is set to IEPxR1 and the Loop Counter is decremented. When there is a match and Loop Counter=1, the Loop Counter is loaded with the Loop Reload Value and the loop is exited. It is noted that the “x” in EPLOOPx, IEPxR0, IEPxR1 and IEPxR0 is equal to the BPID value 0, 1, 2 or 3.

The EPLOOPIx instruction 720 shown in FIG. 7C sets up and executes a program loop beginning with the next sequential instruction. The instruction eventpoint register (IEPxR1) is loaded with the address of the next sequential instruction. The instruction eventpoint register (IEPxR0) is loaded with the address of the last instruction in the loop, which is the sum of the address of the EPLOOPI instruction and the 10-bit unsigned displacement UDISP10. The instruction eventpoint register (IEPxR2) is loaded with the unsigned 12-bit value LoopCnt, placing the value in both the upper and lower half-words. The appropriate instruction eventpoint control field IEPx, IEP0–IEP3, in the IEPCTL0 register is loaded with the hexadecimal value 0x18. If the loop counter (IEPxR2) is non-zero, execution proceeds with the next sequential instruction. If the loop counter is zero, the body of the loop is skipped and execution proceeds with the next sequential instruction after the IEPxR0. While the loop counter is greater than zero, a loop is active and each instruction address is compared to the IEPxR0. When there is a match and the loop counter is greater than one, PC is set to IEPxR1 and the loop counter is decremented. When there is a match and the loop counter equals one, the loop counter is loaded with the loop reload value and the loop is exited.

The EPLOOP and EPLOOPI instructions 700 and 720 are used to provide a low latency mechanism for a select group of the eventpoints. The exemplary ManArray architecture allows up to four nested eventpoint loops so as to better optimize utilization of the eventpoint hardware and conserve bits in the EPLOOP instructions. Specifically, the four eventpoints are specified in the EPLOOP and EPLOOPI instructions, by means of the BPID encoding in bits 23–22, for this purpose.

An exemplary pipeline timing diagram 800 for a ManArray processor implementation for the start up sequence of the EPLOOPx instruction 700 for a multi-instruction program loop is shown in FIG. 8. It is noted that for the EPLOOPx instruction the loop count is loaded using the SSPR instruction prior to issuing the EPLOOPx instruction. EPLOOPIx simplifies this further by not requiring a separate load of the loop count value as it is already contained in an immediate field 722, bits 21–10 in the instruction 720 of FIG. 7C.

The pipeline timing diagram 800 of FIG. 8 is made up of five columns: a clock cycle indicator column 802 which is set to zero as a reference point for the fetch of the EPLOOPx instruction, an EP compare column 804 indicating when the compares for a program loop occur, a fetch column 806 indicating the instruction fetch sequencing, a decode column 808 indicating the operations that occur during decode, and an execute column 810 indicating the operations that occur during execute. Beginning with cycle 0 shown in row 812, the EPLOOPx instruction is fetched and prior instructions continue to execute. In cycle 1 shown in row 814, the first instruction of the program loop is fetched. In the decode phase, the end address for the loop is calculated as program counter value plus a 10-bit displacement obtained from the EPLOOPx instruction. The program counter is held, and a no-operation (NOP) instruction is inserted in the pipe. Also, in the execute phase, the previous instruction to the EPLOOPx instruction is executed. In cycle 2 shown in row 816, no new instruction is fetched as the first instruction of the program loop has already been fetched. In the decode phase, the hardware executes the NOP that was inserted in the pipe in the previous cycle. In the execute phase, the end address is sent to the IEPx module on the SPR bus and loaded into IEPxR0. The program counter value is loaded into IEPxR1 representing the start address of the loop. The program counter is still held, and a second NOP instruction is inserted in the pipe. In cycle 3 shown in row 818, the first compare of IPExR0 loop start address with the program counter is done with a match signal generated. The first instruction of the loop is allowed to continue in the pipe. In the decode phase, the second inserted NOP is decoded. In the execute phase, the first inserted NOP is executed. In cycle 4 shown in row 820, the next or second instruction of the program loop is fetched. In the decode phase, the first instruction of the loop is decoded. In the execute phase, the second inserted NOP is executed. In cycle 5 shown in row 822, the processing continues to proceed with fetching, decoding, and executing the instructions in the program loop.

Data Eventpoints

FIG. 9 shows an exemplary data eventpoint module 900 having three data eventpoint registers, comprising two half-word 16-bit registers 916 and 918, and two other parameter registers 924 and 928. Data eventpoint module 900 also includes a control register 914, eventpoint decode and control logic 910 and the necessary interfaces required for a generalized data eventpoint architecture in accordance with the present invention. The data eventpoint control register 914 is one of a plurality of byte-wide control registers, with one byte-wide register assigned for each data eventpoint. The data eventpoint control registers for up to three data eventpoints may be suitably stored in an SPR file made up of a 32-bit register as shown in the tables below:

SP/PE0 DEPCTL0 3 3 2 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 R P P P R D D D S P T DEP2 S P T DEP1 S P T DEP0 e E E E e M A M 2 2 2 1 1 1 0 0 0 s D D D s A M A e E E E e S S S r P P P r e e e v 2 1 0 v 1 1 1 e e 2 1 0 d d

PEx DEPCTL0 3 3 2 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 Reserved P Reserved D Reserved S P T DEP0 E M 0 0 0 D A E S P e 0 1 0 In the above tables,

DEPx Specifies how DEPxRO, DEPxR1 and DEPxR2 are used for detecting data events and generating corresponding actions. Sx Sx = 0: Do not output debug interrupt on match event. Sx = 1: Debug interrupt is driven by control logic on match event. Px Px = 0: Pass InTrigger signal to OutTrigger signal (except when generating an OutTrigger from control logic). Px = 1: Always generate OutTrigger from control logic. Tx Tx=0: InTriggerFF always set to ‘1’ during monitoring. Tx=1: InTriggerFF set by InTrigger signal (previous EP's OutTrigger signal). DMASelx Select DMA Lane address for DEPx. For DMA synchronization DEP control codes. DMASelx = 0: Monitor DMA Lane 0 address. DMASelx = 1: Monitor DMA Lane 1 address. PEDEPx For SP/PE0, these bits indicate whether the DEP is configured to monitor SP or PE0 addresses. PEDEPx = 0: Monitor SP data addresses. PEDEPx = 1: Monitor PE0 data addresses. It is noted that in the exemplary implementation specified by the control register definition above, additional data eventpoints can be added by using another data eventpoint control register for each group of up to three data eventpoints. The control register 914 represents one of the byte fields from the DEPCTL0 and passes the 8-bits of control information on signal lines 929 to the decode and control logic 910.

Further details for the three other data eventpoint registers 924 (DEPxR0), 928 (DEPxR1), and 16-bit half-word registers 916 and 918, DEPxR2.H1 and DEPxR2.H0 respectively, are shown in the tables below:

DEPxR0 3 3 2 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 parameter value

DEPxR1 3 3 2 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 parameter value

DEPxR2 3 3 2 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 DEPxR2.H1 DEPxR2.H0 The register DEPxR0 924 holds a programmer-specified value, loaded over the SPR bus 917, which consists of address, data, and controls, that is to be compared with the bus/signals 921 as selected by the control register 914 DEPCTLz. By encoded bit field. In the data eventpoint module 900 of FIG. 9, multiplexer 923 provides a mechanism to select either the load effective address (LEA) or the store effective address (SEA) as the value on the multiplexer output 921 to be compared. This mechanism provides the capability to trigger an event on a match of a load data effective address or a store data effective address. The register DEPxR1 928 holds a programmer specified data value, loaded over the SPR bus 917, which consists of address, data, and controls, that is to be compared with either a selected data value 975 that represents a masked 950 LDATA or SDATA bus by use of the DEPxR2.H1 and DEPxR2H0 or one of the bus/signals 971 as selected by the control register 914 DEPx encoded bit field. It is noted that the load data (LDATA) bus 977 and store data (SDATA) bus 979 are latched data values stored in a hidden scratch pad register due to the execution pipeline in use for the ManArray processor. The DEPxR2.H0 count register 918 can also act as an eventpoint counter which indicates a count of 1, a count of 0, or if the count is greater than 1. The decode and control logic 910 operation is described in detail in operation tables 1010, 1015, 1020, 1030, 1040, 1050, 1060, 1070, 1080, 1090, and 1095 shown in FIGS. 10A–10J. These tables are constructed in the same manner as the instruction eventpoint logic descriptions of FIGS. 6A–6G. The control value column 1012 of each figure provides a description of the logic operation for the programmed control value also indicated in the same column. Matches with the load effective address (LEA), the store effective address (SEA), load data (LDATA), and/or store data (SDATA) of the data memory accesses are enumerated as options for the data eventpoint logic. Background DMA operations, described in greater detail below, are also presented with use of data eventpoints in FIGS. 10I and 10J. It is appreciated that other eventpoint operations are easily achieved for numerous purposes using this architectural and programming approach for eventpoints.

When a data eventpoint is detected, one option selected by the eventpoint logic is to cause an EP interrupt 947 that changes the program flow to a debug interrupt routine useful for analysis and problem solving. The EPxOut signal 976 of FIG. 9 is asserted in data eventpoint control modes when the eventpoint counter is being used as a semaphore and an address match has occurred with a non-zero count present. For example, this approach is used for DMA data flow control by connecting the signal to inputs in the DMA controller which cause semaphore increments. Each data event point provides an EPxOut signal to a controlling event action module such as a DMA controller. The use of eventpoints in DMA operations is discussed further after eventpoint chaining and eventpoint status are discussed.

Eventpoint Chaining

FIG. 11 depicts an eventpoint chaining apparatus 1100 which may be advantageously used in an exemplary implementation of the ManArray architecture similar to the system shown in FIG. 1 is discussed further below. The eventpoint chaining apparatus 1100 uses the OutTrigger (OutTrig) signal, for example signal 1101 from an eventpoint module 1104 as an input InTrigger (InTrig) signal 1103 for the next eventpoint module 1102. Eventpoint modules 1102–1118 are linked together in a circular chain. The chaining of eventpoints, in reference to FIGS. 5 and 9, is accomplished through the use of the OutTrigger signal 545 or 945 and the InTrigger signal 515 or 915. The OutTrigger signal 545 or 945 is selected by multiplexer 508 or 908 as controlled by control signal 543 or 943, when the OutTrigger path 941 is enabled and an eventpoint is discovered. Alternatively, the InTrigger signal 515 or 915 can be passed through the eventpoint module as selected by multiplexer 508 or 908 and controlled by control signal 543 or 943. The InTriggerFF (InTFF) latch 512 or 912, when enabled, captures the state of the InTrigger signal 515 or 915 which is sent to the decode and control logic 510 or 910 over line 527 or 927. The InTFF latch, 512 or 912, is cleared whenever

-   -   A value is written to the control register field associated with         its eventpoint, or     -   An eventpoint match has occurred, or     -   The eventpoint is disabled.         The OutTrigger output 545 or 945 from an eventpoint module         connects to the InTrigger input 515 or 915 of the assigned         eventpoint module.

FIG. 11 depicts an exemplary chaining with a mixture of six instruction eventpoints SP/PE0 IEP5-0 and three data eventpoints DEP2-0 in the SP/PE0, such as the SP/PE0 101. It is noted that the specific order of the chaining shown represents one choice as used in an exemplary implementation of a 2×2 ManArray processor. It is further noted that while the chaining of data eventpoints between PE is not shown and the use of multiple data eventpoints in each PE is not shown in FIG. 11, these options are not precluded by the architecture of the present invention. The OutTrigger (OutTrig) from each eventpoint module is connected to the InTrigger (InTrig) of the connecting eventpoint module.

Eventpoint Status

Eventpoints may be programmed with various control options. The purpose of some of these options is simply to detect when a particular event or sequence of events has occurred. The EPSTAT register is used to capture event occurrence for those events which generate an EP interrupt so that if multiple eventpoint interrupts are being tracked, they may be distinguished. Suitable EPSTAT registers and the chosen definition for the status bits for the exemplary 2×2 ManArray implementation are shown in the following format tables for a 32-bit example. Since the ManArray processor merges the SP array controller with PE0 of the PE array, the EPSTAT register data eventpoints are shared between the SP and the PE0. In other implementations, this organization may not exist, but the concepts and use of the eventpoints and the EPSTAT registers still applies.

SP/PE0 EPSTAT (Read-only, SP SPR) Reset Value = 0x00000000 3 3 2 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 Reserved I I I I I I Reserved D D D E E E E E E E E E V V V V V V V V V 5 4 3 3 1 0 2 1 0

PE EPSTAT (Read-only, PE SPR) Reset Value = 0x00000000 3 3 2 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 Reserved D E V 0

DEVx This bit is set when a match event generates an EP interrupt for Data Event Point ‘x’. (Not all control codes that may be programmed cause an interrupt to be generated on a match event, and for these cases the DEVx bits are not set). 0 = event has not occurred 1 = event has occurred IEVx This bit is set when a match event generates an EP interrupt for Instruction Event Point ‘x’. (Not all control codes that may be programmed cause an interrupt to be generated on a match event, and for these cases the IEVx bits are not set). 0 = event has not occurred 1 = event has occurred

FIG. 11 further illustrates that for each eventpoint module 1102–1123 an EP Interrupt can be generated. All instruction 1126 and data 1128 eventpoint EP interrupts are logically ORed together by OR gate 1125 to provide the eventpoint interrupt signal to the SP interrupt control unit 1130. Within the SP and PEs, the EPSTAT registers are used to store event status from SP or PE resident event point control logic. The EP status saved in the EPSTAT registers indicates when an event point has matched its event criteria and generated an EP interrupt. A read from this register returns the status while a write to this register with any data clears the status flags. These bits are also cleared at reset. It is noted that other formats and bit definitions are not precluded. For example, status indication on any match event can be provided in addition to the above noted match and EP interrupt event status.

The SP/PE0 and each of the other PEs contains an EPSTAT register that is visible in their own SP and PE SPR address spaces. In the SP/PE0, the SP EPSTAT register can be read by use of the LSPR.S instruction illustrated in FIGS. 2A and 2B. In the PEs, the PE EPSTAT register can be read by use of the LSPR.P instruction also illustrated in FIGS. 2A and 2B. In the exemplary implementation of FIG. 1, each PE's EPSTAT register contains only a single status bit that indicates if the PE generated a match event which caused an EP interrupt. In this illustrative example, each PE, such as one of the PEs 151, 153 or 155 of FIG. 1, supports one data eventpoint requiring only three parameter registers and one control register. Specifically, PE event status may be read using an LSPR.P instruction along with SPRECV instructions to retrieve each PE's status to the SP register file. The SPRECV instruction causes the specified SP target register to receive data from PE0's cluster switch input port. Even though the exemplary implementation describes only a single eventpoint per PE, multiple data eventpoints per PE are not precluded and may be readily implemented utilizing the present teachings.

In the SP and depending upon the implementation and with two eventpoint control register specifications, up to eight instruction eventpoints can be set up. It will be recognized that additional eventpoints can be added as desired. The eventpoints can be shared and combinations of capabilities provided. For example, 1 in the SP, two nested EP loops with two background DMA operations with two instruction and two data debug eventpoints can be programmed. In addition, highly advantageous capabilities, as described in the control value and logic description of FIGS. 6A–6F and 10A–10G, are provided to the general programmer.

Eventpoint Background DMA

One of the many unique uses of the present eventpoint architecture is its use to initiate and control background direct memory access (DMA) operations to efficiently move data while normal processing continues. For example, the managing of a data buffer 1200, such as is shown in FIG. 12A, where a local memory data segment M is split into two buffer portions, a Buf1 1202 and a Buf2 1204. In a typical application, such as processing an MPEG compressed bit-stream, it is desirable to achieve efficient processing of the data without using a lot of performance-limiting memory management steps. The eventpoint architecture of the present invention advantageously achieves this goal as discussed further below. In one approach using data-access triggered DMA, the following requirements are assumed:

-   -   A stream of variable-length data elements is consumed from a         circular buffer in memory which is of length BUFSIZE words.     -   The elements are processed as they are read. A new word is         loaded into the buffer at intermittent intervals based on the         size of the variable length code (vlc).     -   Conditional execution is used to perform the LOAD of a new word,         and a load does not occur on every pass through the “get new         vlc” function. Thus, there is not a direct correlation between         fetching of an instruction address and consumption of data.     -   It is desired to trigger a background refill operation after N         data accesses from the buffer, not N instruction fetches from a         particular address. In this case, the background operation is a         DMA operation to refill a buffer.     -   It is necessary to prevent overrun of the buffer, in other         words, to prevent DMA writes on top of unprocessed data.     -   It is necessary to prevent underrun, in other words, to prevent         the case where the processor reads ahead of data.     -   It is assumed a ping-pong buffer is accessed in a circular         fashion by the SP code.     -   Buffer halves are labeled Buf1 and Buf2, each of length N.     -   A DMA transfer is set up to move N words of data at a time to a         circular buffer of size 2N, that is the core transfer count         (CTC) of data to be transferred to the core is N, but the buffer         size of the circular transfer is 2N.     -   The DMA transfer uses a semaphore to indicate when it is allowed         to fill a buffer. Initially, the DMA semaphore is set to 2,         indicating it can fill both buffers. Each time the DMA unit         decrements CTC to zero, i.e., transfers N data values, it also         will decrement and check the semaphore. If the semaphore is         non-zero after the decrement, the transfer reloads CTC with N         and continues the transfer, filling the other half of the buffer         (Buf2). If the semaphore has been decremented to zero, then the         DMA waits until it is non-zero to reload CTC and continue with         another transfer.     -   Whenever N data elements are transferred (CTC reaches zero), the         DMA sends a signal to an eventpoint (EP) module which causes it         to increment its count value.     -   Whenever the SP accesses a data address (via a LOAD instruction         in this case) that has been programmed into the EP block, the EP         sends a signal to the DMA unit which causes its semaphore to         increment.     -   If the EP count value is zero, then the SP will optionally stall         to wait for data to arrive.     -   If the EP count is non-zero, the EP count is decremented and the         SP continues.     -   If both the DMA and SP access the counter simultaneously and the         count remains the same, the SP is allowed to continue.     -   Since a Data EP can only specify up to 2 address parameters in         the example implementation, the count value can be up to two.     -   Signaling from DMA to EP block is done by each DMA Lane         Controller which routes its CTCzero interrupt signal to 1 of the         IEP and 1 of the DEP modules of the SP.

In another approach, FIG. 12B contains an outline of a simple program routine 1220 set up as a data dependent loop to process an unknown quantity of data elements. The data processing is to continue until an end-of-data code is decoded from the received encoded bit-stream stored in the buffers prior to processing. Initially, a DMA for Buf1 is started, after which the program routine starts at address L0. The routine 1220 then loops until an end-of-data code is decoded. The routine accesses data from the memory buffer by use of a load modulo index type of instruction that begins addressing at the address A, the start address of FIG. 12A, and automatically wraps the address around, at the end of Buf2, to the beginning of Buf1, address A. The three eventpoints used are shown in table 1240 of FIG. 12C. The first eventpoint is an instruction event point that is chained to the two data eventpoints, DEP0 and DEP1. The IEP0 eventpoint, control value 0PT00001 670 of FIG. 6F, is setup with IEP0R0=not used, IEP0R1=XL, address of DMA-not-complete-do-something-else program, and IEP0R2.H0=IEP0R2.H1=2, indicating at the start that either Buf1 or Buf2 has data. The IEP0 counter is set up by its decode and control logic to increment the counter upon receiving a DMA transfer complete signal 509 (FIG. 5). The counter decrements whenever an InTrigger event occurs. The instruction eventpoint, when InTrigger occurs and the count is a one, causes the vector address X1 to be loaded into the PC thereby changing the program flow to the DMA-not-complete-do-something-else routine. In normal operation, the count is incremented by the DMA transfer complete signal prior to receiving an InTrigger signal and the IEP0 eventpoint will not occur. If the DMA is held up and the DMA operation is not complete, only then will the program reach the special routine. The other two background DMA data eventpoints are set up for interfacing with the system DMA unit. The first one uses data eventpoint0 (DEP0) with DEP0R0=A, the Start address of Buf1, DEP0R1=C, the start of Buf2 address, and DEP0R2.H0=0, DEPOR2.H1=0, Buf2 empty state. The second one uses data eventpoint1 (DEP1) with DEP1R0=C, the start of Buf2 address, DEP1R1=A, the start of Buf1 address, and DEP1R2.H0=1, DEP1R2.H1=0, Buf1 full state. It is further assumed for this example, that the size of Buf1 is equal the size of Buf2 (FIG. 12A), and the DMA unit is set up previous to the program routine to transfer a buffer size of N beginning at a start address that is passed to the DMA hardware when the background DMA is initiated.

The sequence of events is as follows assuming Buf1 is fully loaded with the initial data at the start of the program. The program routine begins processing data in Buf1, which on the first access at address A the DEP0 eventpoint is detected which initiates a DMA operation to load data into Buf2 beginning at address C, which address value is passed to the DMA hardware unit over the EP1Bus 981. When DEP0 is activated, the count in IEP1R2.H0 reloads a 0 indicating that Buf2 is empty. The program routine continues processing the data in Buf1 while the DMA unit in the background independently loads the next set of data elements into Buf2. At the end of the DMA transfer of data to Buf2, the DMA unit generates a DMA complete signal which increments the Buf2 count in DEP0R2.H0 to 1 indicating Buf2 is now full and processing can proceed. Meanwhile, the processing of Buf1 data has continued until it reaches the first data element in Buf2 at address C and DEP1 eventpoint is triggered reloading DEP1's count DEP1R2.H0 to zero indicating Buf1 is now empty and DEP1R1=A is passed to the DMA unit over the EP0Bus 981. The DMA unit now initiates the background loading of Buf1 while the program is allowed to continue with the processing of Buf2 data. The program routine continues processing the two buffers until the end-of-data code is decoded. If the program ever tries to access data from Buf1 at address A, or Buf2 at address C, and the DMA transfer has not completed for that buffer, instruction eventpoint IEP0 is triggered, indicating the background DMA has not completed operation.

This concept is extended by allowing address masking in the address compare, for example, by using a single address with a mask register, and then supporting multiple address matching for buffer sizes that are a power of 2. Since masking is already allowed for the data compares, this approach may be readily implemented. Address masking is also useful for trapping when access to specified regions of memory by either instruction fetch or data fetch is attempted.

The generalized eventpoint architecture shown in FIGS. 5 and 9 and discussed above in detail includes the advantageous capabilities highlighted in the partial list that follows: auto looping, auto looping with loop skip if count is zero, auto looping where an InTrigger signal can be used to exit or skip the loop, background DMA, initiating a timer from some data or instruction eventpoint, and cache pre-fetch operation.

While the present invention has been disclosed in the context of various aspects of presently preferred embodiments, it will be recognized that the invention may be suitably applied to other environments and applications consistent with the claims which follow. 

1. An eventpoint chaining apparatus for generalized event detection and action specification in a processing environment comprising: a first processing element having a programmable eventpoint module with an input trigger (InTrig) input, the first processing element detecting an occurrence of a first processor event (p-event) and producing an OutTrigger (OT) signal; a second processing element having a programmable eventpoint module with an input trigger (InTrig) input which receives the OT signal from the first processing element, the second processing element detecting an occurrence of a second p-event and producing, in response to the OT signal received from the first processing element and the detected second p-event, an eventpoint (EP) interrupt signal; and a sequence processor interrupt control unit for receiving the EP interrupt signals indicating the occurrence of both the first and second p-events and causing a processor action (p-action) in response to the occurrence of both the first and second p-events.
 2. The apparatus of claim 1 wherein each of said eventpoint modules further comprises: means for detecting a generalized processor event (p-event) comprising a change of state it is desirable to recognize; and means for implementing a generalized processor action (p-action) in acknowledgement in response to the detection of the generalized p-event.
 3. The apparatus of claim 1 wherein the first processing element is a sequence processor.
 4. The apparatus of claim 1 wherein the first and second processing elements are array processor elements.
 5. The apparatus of claim 1 wherein the first and second processing elements both further comprise a special purpose register (SPR) or registers for the storage of the eventpoint parameters.
 6. The apparatus of claim 5 wherein eventpoints are separated into two basic classes, instruction eventpoints and data eventpoints and both classes of eventpoints are stored in the SPR file.
 7. An eventpoint chaining apparatus for generalized event detection and action specification in a processing environment comprising: a processing element having at least a first and a second programmable eventpoint module, each programmable eventpoint module having an input trigger (InTrig) input, a first output, and a second output; the InTrig of the second eventpoint module connected to the first output of the first eventpoint module, the first programmable eventpoint module detecting an occurrence of a first processor event (p-event) and producing an OutTrigger (OT) signal over the first output of the first programmable eventpoint module; and the second programmable eventpoint module receiving the OT signal over the InTrig input, detecting an occurrence of a second p-event and, in response to the received OT signal and detected second p-event, producing an eventpoint (EP) interrupt signal over the second output to cause a processor action (p-action) in response to the occurrence of both the first and second p-events.
 8. The apparatus of claim 7 wherein the processing element is a sequence processor.
 9. The apparatus of claim 7 wherein one eventpoint module is for an instruction eventpoint and the other eventpoint module is for a data eventpoint.
 10. The apparatus of claim 7 wherein both eventpoint modules are for instruction eventpoints.
 11. The apparatus of claim 7 wherein both eventpoint modules are for data eventpoints. 